package uk.org.aspellclark.gedcom.model.records;

import java.util.List;

import uk.org.aspellclark.gedcom.model.ChangeDate;
import uk.org.aspellclark.gedcom.model.structures.NoteStructure;

/** <pre>SUBMISSION_RECORD:=
    n @XREF:SUBN@ SUBN                         {1:1}
        +1 SUBM @XREF:SUBM@                    {0:1} p.28
        +1 FAMF &lt;NAME_OF_FAMILY_FILE>       {0:1} p.54
        +1 TEMP &lt;TEMPLE_CODE>               {0:1} p.63
        +1 ANCE &lt;GENERATIONS_OF_ANCESTORS> {0:1} p.50
        +1 DESC &lt;GENERATIONS_OF_DESCENDANTS> {0:1} p.50
        +1 ORDI &lt;ORDINANCE_PROCESS_FLAG>   {0:1} p.57
        +1 RIN &lt;AUTOMATED_RECORD_ID>       {0:1} p.43
        +1 &lt;&lt;NOTE_STRUCTURE>>         {0:M} p.37
        +1 &lt;&lt;CHANGE_DATE>>          {0:1}</pre>
The sending system uses a submission record to send instructions and information to the receiving
system. TempleReady processes submission records to determine which temple the cleared records
should be directed to. The submission record is also used for communication between Ancestral File
download requests and TempleReady. Each GEDCOM transmission file should have only one
submission record. Multiple submissions are handled by creating separate GEDCOM transmission
files.
 */
public class SubmissionRecord extends GedcomRecord {
	public String famf;
	public String temp;
	public String ance;
	public String desc;
	public String ordi;
	public String rin;
	public List<NoteStructure> note;
	public ChangeDate changeDate;
}
